System and method for converting paper forms to an electronic format

ABSTRACT

A system and method for creating and managing electronic forms is described. The system includes a processor configured to receive an image of a form and receive, via a network interface, form template information specifying at least a first input field. The form template information includes a first input field type selection and first field location information for the first input field. The first input field type is selected from a plurality of input field types and the first field location information is defined relative to the image. The processor stores the form template information within a memory. The electronic form is configured to be rendered by superimposing a representation of the first input field over the image of the form.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of U.S. Provisionalapplication Ser. No. 14/213,905, entitled SYSTEM AND METHOD FORCONVERTING PAPER FORMS TO AN ELECTRONIC FORMAT, filed Mar. 14, 2014,which claims the benefit of priority under 35 U.S.C. §119(e) of U.S.Provisional Application Ser. No. 61/785,236, entitled SYSTEM AND METHODFOR CONVERTING PAPER FORMS TO AN ELECTRONIC FORMAT, filed Mar. 14, 2013,filed on even date herewith, the contents of each of which are herebyincorporated by reference in their entirety for all purposes.

FIELD

The systems and methods of the disclosure relate to creation andmanagement of electronic forms. In particular, but not by way oflimitation, the present disclosure relates to systems and methods thatprovide for conversion of paper forms to electronic forms, systems andmethods that provide for capturing information in the electronic formsand systems and methods for managing the electronic forms among a groupof users.

BACKGROUND

Rapid growth of the mobile workforce has increased the pressure fororganizations to find effective methods for managing data generated inthe field. However, despite the proliferation of mobile electronicdevices, like smart phones and tablet computers, most organizationsstill rely upon paper forms for their data management needs because ofthe familiarity and ease of use they have with their paper forms, andthe complexities that come from converting these paper forms toelectronic format. In fact, even if paper forms are converted toelectronic format there often remains a need to easily render forms backto paper format when they must be distributed to customers, suppliersand colleagues. In addition, while there are clear and recognizedadvantages to collecting and managing data electronically, mostorganizations are ill equipped to deal with the intricacies of datasynchronization, management, storage and replication. And even iforganizations were capable of managing their data, there is minimalvalue if they can't simply and effectively share the data and mine itfor improved business intelligence. Ultimately, despite a desire forchange, the perceived benefits of electronic data management are oftennot enough to replace good old-fashioned paper forms for mostorganizations.

Although paper forms and current electronic information systems arefunctional, they are not efficient or otherwise satisfactory.Accordingly, a system and method are needed to address the shortfalls ofpresent technology and to provide other new and innovative features.

SUMMARY

Exemplary embodiments of the teachings disclosed herein are shown in thedrawings are summarized below. These and other embodiments are morefully described in the Detailed Description section. It is to beunderstood, however, that there is no intention to limit the inventionto the forms described in this Summary or in the Detailed Description.One skilled in the art can recognize that there are numerousmodifications, equivalents and alternative constructions that fallwithin the spirit and scope of the disclosed teachings as expressed inthe claims.

In one aspect, an exemplary method of creating an electronic form inaccordance with the disclosure includes receiving an image of a form,and receiving form template information specifying at least a firstinput field, the form template information including a first input fieldtype selection and first field location information for the first inputfield wherein the first input field type selection is selected from aplurality of input field types and the first field location informationis defined relative to the image. The method further includes storingthe form template information within a memory, where the electronic formis configured to be rendered by superimposing a representation of thefirst input field over the image of the form.

In another aspect, an exemplary method in accordance with the disclosureincludes receiving a selection of an electronic form, rendering, by adisplay of a device, an image of an original form upon which theelectronic form is based, superimposing a plurality of input fields overa corresponding plurality of fields of the original form, and selectingone of the input fields to receive user input.

In another aspect in accordance with the disclosure, a method ofinteracting with an electronic form includes retrieving an electronicform template from a computer readable storage medium, the electronicform template being useable to generate the electronic form. Theelectronic form template includes first data representing an image of aform, second data defining a position of at least one input fieldrelative to the image of the form, and third data representing a firstfield type associated with the first input field, the first field typebeing one of a plurality of field types. The method further includesdisplaying, upon a display device, the image of the form andsuperimposing a representation of the first input field over the image,receiving, via the first input field, first input data, andelectronically storing the first input data.

In another aspect in accordance with the disclosure, a system forcreating an electronic form includes memory and a processor coupled tothe memory. The processor is configured to receive an image of a form,receive, via the network interface, form template information specifyingat least a first input field. The form template information includes afirst input field type selection and first field location informationfor the first input field where the first input field type selection isselected from a plurality of input field types and the first fieldlocation information is defined relative to the image. The processor isfurther configured to store the form template information within thememory. The electronic form is configured to be rendered bysuperimposing a representation of the first input field over the imageof the form.

In another aspect in accordance with the disclosure a system includesmemory and a processor coupled to the memory. The processor isconfigured to receive a selection of an electronic form, render, by adisplay of a device, an image of an original form upon which theelectronic form is based, superimpose a plurality of input fields over acorresponding plurality of fields of the original form, and select oneof the input fields to receive user input.

In another aspect in accordance with the disclosure, a system ofinteracting with an electronic form includes a memory and a processorcoupled to the memory. The processor is configured to retrieve anelectronic form template from a computer readable storage medium. Theelectronic form template is useable to generate the electronic form andincludes first data representing an image of a form, second datadefining a position of at least one input field relative to the image ofthe form, and third data representing a first field type associated withthe first input field, the first field type being one of a plurality offield types. The processor is further configured to display, upon adisplay device, the image of the form and superimposing a representationof the first input field over the image, receive, via the first inputfield, first input data and electronically store the first input data inthe memory.

In another aspect in accordance with the disclosure, a non-transientcomputer readable medium stores program code which, when executed by aprocessor, causes the processor to receive an image of a form, andreceive form template information specifying at least a first inputfield. The form template information includes a first input field typeselection and first field location information for the first input fieldwhere the first input field type selection is selected from a pluralityof input field types and the first field location information is definedrelative to the image. The program code further causes the processor tostore the form template information within a memory. The electronic formis configured to be rendered by superimposing a representation of thefirst input field over the image of the form.

In another aspect in accordance with the disclosure, a non-transientcomputer readable medium stores program code which, when executed by aprocessor, causes the processor to receive a selection of an electronicform, render, by a display of a device, an image of an original formupon which the electronic form is based, superimpose a plurality ofinput fields over a corresponding plurality of fields of the originalform, and select one of the input fields to receive user input.

In yet another aspect in accordance with the disclosure, a non-transientcomputer readable medium stores program code which, when executed by aprocessor, causes the processor to retrieve an electronic form templatefrom a computer readable storage medium. The electronic form template isuseable to generate the electronic form and includes first datarepresenting an image of a form, second data defining a position of atleast one input field relative to the image of the form, and third datarepresenting a first field type associated with the first input field,the first field type being one of a plurality of field types. Theprogram code further causes the processor to display, upon a displaydevice, the image of the form, superimpose a representation of the firstinput field over the image, receive, via the first input field, firstinput data and electronically store the first input data.

As previously stated, the above-described embodiments andimplementations are for illustration purposes only. Numerous otherembodiments, implementations, and details of the invention are easilyrecognized by those of skill in the art from the following descriptionsand claims.

BRIEF DESCRIPTION OF THE DRAWINGS

Various objects and advantages and a more complete understanding of thepresent disclosure and teachings herein are apparent and more readilyappreciated by reference to the following Detailed Description and tothe appended claims when taken in conjunction with the accompanyingDrawings wherein:

FIG. 1 illustrates details of a system on which embodiments of themethods described herein may be implemented;

FIG. 2 illustrates details of an embodiment of an example clientapplication for use on a user device;

FIG. 3 illustrates details of an example server system for use with aclient application such as shown in FIG. 2;

FIG. 4 illustrates a flowchart of an exemplary process for creating anelectronic form template in accordance with the disclosure;

FIG. 5 shows an image of an electronic form used in the process of FIG.4;

FIG. 6 shows a screenshot of a user interface used in the process ofFIG. 4;

FIG. 7 shows another screenshot of a user interface used in the processof FIG. 4;

FIG. 8 shows a pair of screenshots showing interconnections betweenitems in form view and respective items in a field view created by theprocess of FIG. 4;

FIG. 9 shows a screenshot of a user interface used in the process ofFIG. 4;

FIG. 10 illustrates a flowchart of an exemplary process for interactingwith an electronic form created by the process of FIG. 4 in accordancewith the disclosure;

FIG. 11 shows another screenshot of a user interface used in the processof FIG. 10;

FIG. 12 shows a completed electronic form created by the process of FIG.10;

FIG. 13 shows a pair of screenshots showing interconnections betweenitems in form view and respective items in a field view created by theprocess of FIG. 10;

FIG. 14 shows a screenshot of a completed electronic form created by theprocess of FIG. 10;

FIG. 15 illustrates a flowchart of an exemplary process for creating areport using information obtained from forms created by the processes ofFIGS. 4 and 10 in accordance with the disclosure;

FIG. 16 shows a screenshot of a user interface used in the process ofFIG. 15;

FIG. 17 shows a screenshot of another user interface used in the processof FIG. 15;

FIG. 18 shows a screenshot of another user interface used in the processof FIG. 15;

FIG. 19 shows a screenshot of another user interface used in the processof FIG. 15;

FIG. 20 shows a screenshot of another user interface used in the processof FIG. 15;

FIG. 21 shows a screenshot of another user interface used in the processof FIG. 15;

FIG. 22 shows a screenshot of a user interface used to create and manageevents triggered by completion of electronic forms in accordance withthe disclosure;

FIG. 23 shows a screenshot of another user interface used to create andmanage events triggered by completion of electronic forms in accordancewith the disclosure; and

FIG. 24 shows a screenshot of another user interface used to create andmanage events triggered by completion of electronic forms in accordancewith the disclosure.

In the appended figures, similar components and/or features may have thesame reference label. Further, various components of the same type maybe distinguished by following the reference label by a second label thatdistinguishes among the similar components. If only the first referencelabel is used in the specification, the description is applicable to anyone of the similar components having the same first reference labelirrespective of the second reference label.

DETAILED DESCRIPTION

As discussed above, despite the growing adoption and deployment ofmobile electronic devices, like smart phones and tablet computers,organizations still heavily rely upon paper forms for their data captureneeds. These paper forms can vary in nature from checklists, invoices,job activity reports, inventory reports, audits, treatment plans andmuch, much more. There are several reasons why paper is still asignificant data capture method.

First, paper forms provide a familiar user interface. In particular,paper forms may have been used in an organization for many weeks to manyyears with little or no modification. Users have been trained to usethese paper forms and can complete a paper form with or without anyphysical or electronic connection to any back end system.

Second, it has traditionally not been a simple task to convert paperforms to electronic format. In many cases, users must recreate theirform from scratch using an electronic canvas with the resultingelectronic form bearing no resemblance to their existing paper form.Moreover, users must design their electronic forms differently tosupport different platforms like desktop computers, laptop computers,tablet computers and smart phone devices.

Third, the vast majority of organizations do not possess thesophisticated technical resources required to manage the system ofservers, networks, data security practices, and data storage devices tosupport the synchronization and management of mobile data.

Before further describing various aspects and functionality of theelectronic form creation and management methods described herein, it maybe helpful to describe the general context and systems and devices onwhich embodiments may be implemented as shown in FIGS. 1 through 3.

For example, FIG. 1 illustrates details of a system 100 on which variousembodiments may be implemented. System 100 includes one or more(typically many) mobile user devices 120, which may be netbooks, smartphones, personal digital assistants (PDAs), tablets, or other similar orequivalent mobile devices. As shown in FIG. 1, user device 120A is asmart phone and user device 120B is a tablet device, each of whichincludes a client application 122, which may be a customized applicationconfigured to utilize an operating system of the smart phone 120A or thetablet device 120B. The client application 122 enables the smart phone120A or the tablet device 120B to gain access to a central server systemsuch as backend server system 110. Mobile devices of the same accountcan communicate with each other via WiFi without communicating with thebackend server 110 when the web backend is not available. This can bebeneficial when users of the same account are working at a site thatdoes not have coverage with the backend server 110 since the userdevices can still transfer forms to each other when completed or whenthe responsibility for filling in a form transfers from one user toanother.

In addition to mobile user devices 120, the system 100 includesnon-mobile devices 130. Such non-mobile devices 130 may include desktopor notebook computers, for example. Non-mobile user device 130 uses astandardized web browser application 140, such as the Internet Explorer,Firefox, or Chrome browsers. Each of user devices 120A, 120B andnon-mobile device 130 may communicate with the server system 110 viaconnections with a network 115, such as the Internet and/or anothernetwork such as a cellular data network, to server system 110.

For the mobile devices 120A and 120 b, the backend server 110 interactswith the client application 122. The client application 122 can bedistributed to user devices identified in the account informationthrough an application store (not shown) for the device's operatingsystem. Applications stores include, but are not limited to, Apple's AppStore and Google's Google Play. When the client application 122 islaunched, a user authenticates the device/application pair with a username and password. Upon authentication, the client application 122synchronizes with the system databases including a template database 160and a forms database 170. During synchronization, a user devicedownloads all of the template and field information, as well as draftforms (forms in progress) and completed forms relevant to the user'saccount as determined by account configuration parameters in the accountdatabase 150. The client application 122 then stores all of thisinformation in a local database, e.g., the memory 125, on the device.

In addition to synchronizing information at mobile devices upon initialauthentication of the client application 122, synchronization can beperformed with mobile devices 120 and non-mobile devices 130 at regularintervals established by the system and/or account configurationparameters. During synchronization, all updated data stored in the localdatabase on the mobile device 120 and non-mobile devices 130 is securelytransmitted to the template database 160 and the forms database 170 andany applicable updates stored in these databases are downloaded to theclient application 122 or the web browser 140 and stored in the memory125 or template/forms database 135.

Server system 110 may include or be connected to one or more databases.The exemplary system 100 includes an account database 150, the templatedatabase 160 and the forms database 170. The account database 150 storesinformation regarding user accounts and individual users associated withthe user accounts of the system 100. At initial account setup, thebackend server 110 establishes a user account within the accountdatabase 150 including receiving account information from one or moreusers associated with the account. The account information can includethe names of individual users associated with the account as well aslevels of access that individuals have to templates and forms associatedwith the accounts. The account information can also include variousgroups and the users in the groups. Such groups can include workinggroups such as project groups, teams, etc.

Each established account is logically segmented from any other useraccount in the account database 150. The account information alsoincludes configuration information about the account. The accountconfiguration information defines the specific user-generatedconfiguration of the system for the account. The backend server providesutilities structured according to the configuration information. Forexample, multiple users can be added and managed within each account,electronic forms can be created, managed and automatically distributedto users within the account, data collected by all users in the accountcan be aggregated and stored based on the configuration information,data mining and reports can be automatically generated, systemnotifications can be generated based on configurable trigger events andgeneral account management and subscription functions can be maintained.Once an account is created, one or more users may begin the process ofconverting paper forms into an electronic format and begin generatingcompleted forms and reports as supported by the system.

The template database 160 includes various electronic form templatesthat have been created by the methods described herein. Templates aremade up of a plurality of input fields that can be superimposed over animage of a form. The form image could be an original electronic image ofa form such as a PDF of TIFF. Alternatively, the form image could havebeen created by scanning an original paper form. The input fields of atemplate are typically void of information except for default entriesand entries that do not change. A user will fill in the input fields ofa template and the completed template is referred to as a form.

The forms database 170 stores forms that are completed or at leastpartially completed. In other words, when a user downloads a templateand fills in one or more input fields, a form is created and is thenstored in the forms database 170. Users associated with a given accountcan have access to some or all of the forms as determined by the accessrules, and group memberships that are stored in the account database150.

Methods are provided for managing the data acquired by the electronicforms and stored in the forms database 170 and creating custom reportsbased on the stored report data. The methods for creating custom reportsprovide for data mining through the completed forms to retrieveinformation for the customized reports as well as integrating theacquired data with other external systems. The components of the systeminteract with each other using a data synchronization methodology inorder to synchronize updates to templates, completed forms and completedreports.

Server system 110 will generally include other data storage devices aswell as associated hardware, software, memory, peripheral interfacedevices, and the like, including modules to receive and store data andinformation, receive and process input from user devices and associatedbrowsers or client applications, and receive and configure informationfrom users to create templates, to utilize the templates to completeforms, to create reports from the draft forms and completed forms and tomanage trigger events using the methods described below.

At user devices 120A and 120B, the client application program 122 may bedownloaded and stored on the user device 120 to allow customized accessto data and information on the server system 110. The client applicationprogram 122 is stored in memory 125. The memory 125 can also storepreviously downloaded templates and forms (completed forms or in-processforms). Alternately, or in addition, the standardized browserapplication 140 (as shown in non-mobile user device 130) may be providedto allow standardized web access and associated functionality in someimplementations. The web browser application 140 as well as previouslydownloaded templates and forms are stored in a template/forms database135 coupled to or included in the non-mobile device 130.

FIG. 2 illustrates details of an embodiment of a client application 200and associated functional modules. Client application 200 may correspondwith the client application 122 as shown in FIG. 1. Client application200 may include a server system interface module 210 configured toprovide an interface or data interchange with an associated serversystem, such as a server system 110 of FIG. 1. This interfacefunctionality may be provided by other software and/or hardware modulesin the particular user device, such as operating system functions, wiredor wireless interface hardware and software, and the like. Application200 may also include an application core or kernel module 220 configuredto perform the basic functionality described subsequently with respectto client application 122 and/or user device operation. In particular,this functionality may be as illustrated in the figures and describedsubsequently herein. Client application 200 may further include atemplate/forms data module 240 to store data associated with the clientapplication, such as templates and forms previously downloaded and/orcreated by a user, data being processed by the application core 220,data received from the server system 110, and/or other data orinformation.

Client application 200 may include application instructions or computercode in an application module 250. The code or instruction module 250may include a specific series of instructions and steps to perform thefunctions described subsequently herein. The computer code orinstructions may be stored on a computer readable medium configured toprovide instructions to a processor or other similar or analogousdevice, such as a programmable logic device, DSP, etc.

The application module 250, in this exemplary embodiment, includesinstructions or computer codes for implementing a template editor module252, a forms editor module 254, a report editor module 256 and an eventsmanager module 258. The template editor module 252 provides a userinterface to receive inputs to create templates in accordance with themethods described herein. The forms editor module 254 provides a userinterface to receive inputs to utilize the templates previously createdto create filled-in forms in accordance with the methods describedherein. The report editor module 256 provides a user interface to allowa user to retrieve data from selected forms that have been previouslyfilled in order to generate reports in accordance with the methodsdescribed herein. The events manager module 258 provides a userinterface to allow creation of event mechanisms in the templates wherethe event mechanisms are triggered by user definable triggers that occurduring utilization of the templates to create filled-in forms.

Some of the modules 252-258 may be omitted from mobile devices 120and/or non-mobile devices 130, depending on the embodiments. Forexample, in one embodiment, the client application 122 of the mobiledevice 120A only includes the forms editor module 254. In thisembodiment, the mobile device 120A can perform the methods for utilizingalready created templates obtained from the template database 160 tocreate filled in forms. However, in order to create templates, createreports and manage events, the mobile device 120A of this embodimentinteracts with a template editor module 342, a report editor module 346and an events manager module 348 of the backend server 110. Otherembodiments of mobile devices and non-mobile devices can include variouscombinations of the template editor module 252, the forms editor module254, the report editor module 256 and the events manager module 258.

Client application module 200 may further include a user interfacemodule 270 configured to receive input from a user, such as userselections, search data or information, or other information providedfrom a user. In addition, the client application module 200 may includea display interface module 280 configured to provide output informationto a user on a display device (not shown) of a user device, such as anLCD or other display screen.

FIG. 3 illustrates one embodiment of details of aspects of a serversystem 300, which may correspond with server system 110 of FIG. 1.Server system 300 may include a core functional module or kernel 310,which may be configured as a module to control overall operation of thesystem as well as support functionality as described subsequentlyherein. The core module 310 utilizes functions provided by an operatingsystem 350. A network interface module 320 is configured to communicatewith user devices such as mobile devices 120A and 120B or non-mobiledevice 130. A backend system applications module 340 may be coupled tocore module 310 to enable user selection of or targeted selection ofcontent for delivery to users. The backend systems applications module340 may be coupled to databases via a database interface 330. Thedatabase interface 330 can be coupled to databases such as the accountdatabase 150, the template database 160 and the forms database 170 ofFIG. 1.

The backend systems applications module 340, in this exemplaryembodiment, includes instructions or computer codes for implementing atemplate editor module 342, a forms editor module 344, a report editormodule 346 and an events manager module 348. The template editor module342 provides a user interface to receive inputs to create templates inaccordance with the methods described herein. The forms editor module344 provides a user interface to receive inputs to utilize the templatespreviously created to create filled-in forms in accordance with themethods described herein. The report editor module 346 provides a userinterface to allow user to retrieve data from selected forms that havebeen previously filled in order to generate reports in accordance withthe methods described herein. The events manager module 348 provides auser interface to allow creation of event mechanisms in the templateswhere the event mechanisms are triggered by user definable triggers thatoccur during utilization of the templates to create filled-in forms.

Additional interface modules may be included in server system 300,either configured separate or integrated in functionality with othermodules. For example, a user may access the system through a user deviceinterface 370, which may be operated in conjunction with a clientapplication executing on a user device and/or a web browser. Inaddition, a user can access the backend server applications module 340via the user interface module 370 in order to create templates and orenter data into templates to create forms. A display interface module380 provides data and graphics information to be displayed on a displaydevice of a user device or a display device coupled directly to the userdevice interface 370.

The backend system applications module 340 may comprise non-transitorycomputer-readable storage media, such as memory devices or other storagecomponents to store instructions for execution by computer processors.The instructions may be used to implement the various functionsdescribed subsequently herein.

Referring to FIG. 4, a process 400 for creating an electronic formtemplate includes the stages shown. The process 400 can be performed bya user device associated with one of the accounts in the accountdatabase 150. The user device can be one of the mobile devices 120 or anon-mobile device 130, referred to herein as user devices. The userdevices communicate with the backend server 110 or 300, referred to fromherein as the backend server 110. For user devices that do not includethe template editor module 252, the user device will utilize thetemplate editor module 242 of the backend server 110 or 300 to performsome of the actions in the process 400. At stage 405, the user selectsan image of a form to be the background of a newly created electronicform. FIG. 5 shows an exemplary image of a form 500. The form 500 can bea scanned image (PDF, JPEG, or TIFF, for example) of an original paperform or an image of an existing electronic form. The image can be a filestored on one of the user devices, stored on the backend server 110 orstored somewhere on the internet in a “cloud” device such as a drop box.The image of the form is received by the client application 122,communicated to the backend server 110 at stage 405 and stored in thetemplate database 160.

The image of a standard paper form, or an image resembling a standardpaper form, provides an intuitive user interface that allows users toeasily capture and manage information in an electronic format. In thisregard, the most intuitive visual interface is one that mirrors theexisting paper form that users in the account have already been trainedto complete. The layout of the paper form is familiar and users alreadyunderstand the most efficient means to capture information using thepaper form.

The image of the form received at stage 405 serves as the visualreference for the electronic form being created during the process 400.When completed, the electronic form template, including the image of theform is stored in the template database 160 for later reference by otherusers and/or elements of the system, including the client application122 and the web browser 140. From herein, the functions performed by theuser device will be described as being performed by the clientapplication 122, but it is to be understood that the web browser 140 ofthe non-mobile device 130 could also perform these functions. Uponreceiving the image of the form, the client application 122 displays theimage of the paper form 500 as the background of an editor canvas in theclient application 122.

At stage 410, the client application 122 receives form templateinformation specifying one or more input fields corresponding toportions of the form image, such as the form image 500. FIG. 6 shows anexemplary screenshot 600 of a user interface including an editor canvas610, of the client application 122. The screenshot 600 shows a list 605of input field types. The user interface of screenshot 600 provides awhat-you-see-is-what-you-get drag and drop interface to simplify set upof the electronic form. In this exemplary editor canvas 610, a userdefines input fields by dragging field types from the list 605 onto thecanvas 610. The field type list 605 defines several different fieldtypes including, but not limited to, a check box field, a check boxgroup field, a barcode field (not shown), a database field, a datefield, a date and time field, a drop down menu field, an image field, alocation field, a number field, a sketch field, a signature field, atable field, a text field and a time field.

FIG. 7 shows another screenshot 700 of the user interface. In FIG. 7, adrag-and-drop action is depicted. A text box input field type 705 isselected by a user, dragged (as indicated by an arrow 710) to the editorcanvas 610 and positioned at an input field 715 entitled CustomerContact. In response to this drag-and-drop procedure, the clientapplication 122 stores information regarding the field type (Text Box),the location (the x, y location corresponding to the Customer Contactfield 715). In addition, the user has titled the Text Box input field“Text Box 2.” This title is also stored in association with theinformation regarding the Text Box 2 input field. The client application122 also stores an entry 725 in a Current Fields box 720 which lists thenewly created Text Box 2 as one of the Current Fields in Page 1 of thecurrent template being created.

For each field type selected at stage 410, the user may modify specificproperties including, but not limited to, font name, font size, color,row height, automated formatting and more. In addition, the user maydefine default values for fields using elements that include, but arenot limited to, static values, calculations, database access andconditional logic. These default value settings are used to provideautomation to the electronic form to simplify data collection andmanagement as well as improve data capture, accuracy and consistency.

As input field types are added to the canvas 610, the client application122 logs the x and y spatial coordinates of the input field typesrelative to the background image and stores these coordinates along withthe parameters of each field in the memory 125 (or the template/formsdatabase 135) and communicates the parameters to the backend server 110to be stored in the template database 160. This approach of providing avisual reference makes it easy for a user to simply place each field inits appropriate position on the document and size the field to fit thefields on the image of the form.

A major difference between this method and other previous methods isthat the previous methods take fields and relate each field to anelectronic entry. The method used in the process 400 uses locations onthe form and relates those locations to an electronic entry and thelocation is an intricate part of the electronic form. In addition, theelectronic entry includes information describing a field type of aplurality of different form field types where the different field typesare each configured to provide a different user interface to receiveinput to complete the electronic form.

The field type list 605 includes a check box field type and a check boxgroup field type. These “check box” related field types include severaldifferent types of selection mechanisms besides just checkboxes. Theselection mechanisms of the checkbox field types include a checkbox, acheck circle, a fill-in circle, etc. The checkbox field type isstand-alone circle or box that can be filled-in or checked or not. Thecheckbox group field type is a selection group such as a check box groupor a fill-in the circle group. In a group, the user can specify how manyof the boxes or circles can be filled in (e.g., only one of two, one ofthree, or whatever, can be chosen) at the same time. The user can alsospecify that the checkbox field type use circles, square, X's, checkmarks, etc. A circle can be used to circle a selection of male/female,for example. You can also have a fill in the circle field to select maleor female.

Check box groups are typically used to select from a group of relatedselections (job status group: complete and not complete, for example).The user selects the locations of each box in the group. The user alsocontrols how many boxes in a group can be selected. A group is a singlefield as far as report generation and importing to other databases.

The field types list 605 also includes a database field type. A databaseis related to a stored group of entities or possible answers (e.g., aCSV file). For example, an author box can be associated with a group ofnames (e.g., employees) and when a user starts entering the name intothe input field, the client application 122 will display possible namesthat complete the name and the user can select the name such that theclient application downloads the name and other related information, asdetermined by the field properties specified by the user.

As an example, a database file (e.g., CSV) can list a plurality ofcustomer contacts including several columns (name, address, phone, etc).The user can choose a field to be a Data Source. The user can upload theCSV file to the client application 122 in association with the Databaseinput field. In this way, a user that is filling in the template createdto include the Database field can import the CSV file to the backendserver 110 and a user can later choose the data from the CSV file thathe wants to fill in the Database field while completing a form based onthe template. In addition, in response to any text that the user enters(e.g., John S), the system will start searching the CSV file for anexisting name starting with John S and bring up the existing data forJohn Smith before the user even finishes typing the name John Smith.

At stage 410, the user can program input fields to have a default value(e.g., for common entries). Fields can also be configured by the user toinclude formulas (e.g., if this field is true, then multiply one valueby another value to arrive at a value for the field). The Default Valuecan also be a database reference. A Database field can be associatedwith multiple cells in a row of the database file. In this way, the usercan fill in several fields of a form by simply creating a formula thattakes a first field value (e.g., customer name), looks up the firstfield in a specified column of a data source, grabs specified othervalues from other columns in the same row as the first field value andimmediately puts the other values in other specified fields (or the samefirst field), as determined by the formula. This eliminates the need forseveral drop-down fields.

Date and date time field types use a date picker and a time picker forentering the value of the field. An image field type can be used toallow a user to load a JPEG file (or other image) into the field of theform. The image is stored in memory by the client application 122 withlocation information in order to appear in a specified portion of theform.

A sketch field type is similar to an image field in that it allows auser to bring in a picture (optionally), but the user can then make linesketches on the field (e.g., draw boxes, add text boxes, hand draw, addsymbols, etc.). A signature field type allows a user to input asignature via a touch screen.

A Table field type allows the user to specify a table with a number ofcolumns and rows (default could be 3 columns and 4 rows) and each columnand row can be sized and named. Each box in the Table can be a differentfield type (e.g., text, drop down, database, time, time/date, currency,phone number, etc.). Each cell/column/row can be sized (font), set tofield type. The user can size the table to line up exactly with theoriginal table in the paper form.

The user can designate a field as a shared field and this would enablethe user to pull this field into another template. This saves time bynot requiring all the characteristics of the field to be created again.This was mainly developed for reporting. As is described below, a reportgenerator can look in other form's shared fields for the exact samefield in order to find the same field name in every form. One could runa report that says anywhere customer name equals name1, pull informationfrom all the forms that have name1 in the “customer name” field.

In Multipage documents, the pages and locations are kept separate andrelated to each field. A field (e.g., customer contact) on one page canbe related to another field on another page and the data can beautomatically sent to the field on the next page. The user simple dragsthe same field from the list of fields on page 1 onto the location onpage 2 (contact name for example). Filling one “customer contact” fieldon one page fills in all “customer contact” fields.

At stage 415, the client application 122 receives information regardingthe layout of the Field View of the input fields of the template. TheField View information determines how the input fields selected by theuser at stage 410 are displayed in a Field View list of fields whichdoes not include the background image of the original form. The FieldView is typically used on smaller devices such as smart phones where afull image of the form, as in the Form View, would not be easilyviewable on the device's small screen.

FIG. 8 shows a pair of screenshots showing interconnections betweenitems in Form View 810 and respective items in a Field View 820. TheForm View 810 is created by the user as discussed above at stage 410.The client application 122 creates the entries in the Field View 820 inresponse to the input fields created by the user. In FIG. 8, inputfields 812, 814 and 816 in the Form View 810 are shown in the Field View820 as fields 822, 824 and 826, respectively.

At stage 415, the user can provide input to the client application thatdetermines how the Field View 820 appears. The user can create sublistsof fields within the list of fields. The order of appearance of thefields in the fields list can be rearranged. As shown in the Field View820, several tabs 830 can be created and fields can be located in thedifferent tabs. The tabs 830 include exemplary tabs including CustomerInformation, Job Details, Parts, Technician Hours, Images/Sketches andAuthorizations. The user can add more Tabs by selecting an “Add” button840.

By including both the Form View 810 and the Field View 820, the templateis configured so that data can be captured efficiently and effectivelyusing both small and large devices as well as mobile and non-mobiledevices.

At stage 420, the client application 122 stores the form templateinformation received at stage 410 and the field view informationreceived at stage 415 within a local memory such as the memory 125and/or the template/forms database 135. In addition, the clientapplication 122 communicates the form template information and the fieldview information to the backend server 110 which in turn stores theinformation in the template database 160. This entire set of templateconfiguration information including Form View and Field View informationis considered by the system 100 to be a form template.

FIG. 9 illustrates a screenshot 900 of an exemplary user interface forallowing a user to upload the template to the backend server 110 to bestored in the template database at stage 420. A browse box 920 isdisplayed by the client device 122 to allow the user to browse localmemory such as the memory 125 of the mobile devices 120 or thetemplate/form database 135 of the non-mobile device 130 to find thenewly created template. The selected template is then uploaded after theuser selects the upload button 925 All elements of the new template arestored in the template database 160, including all fields, theirrespective field types, their location relative to the canvas image, andtheir user-defined properties. Users can subsequently create newfilled-in forms using this template.

At stage 425, the client application, and/or the backend server 110,communicates the form template information and the field viewinformation to other users associated with the account of the user thatcreated the template. The communication at stage 425 can be in responseto a request for the template from one of the mobile devices 120 or thenon-mobile device 130. The communication could also be in response to aperiodic synchronization process with one of the mobile devices 120 orthe non-mobile device 130. The synchronization can be automaticallytriggered due to the template being newly created. If the template, orother templates, is updated at a later time, the synchronization of theupdated templates can also be triggered.

The process 400 is exemplary only and modifications to the process canbe made without departing from the scope of the methods describedherein. For example, stages may be omitted, added or rearranged.

Referring to FIG. 10, a process 1000 for interacting with electronicforms created by the process 400 of FIG. 4 includes the stages shown.The process 1000 can be performed at one of the mobile devices 120 orthe non-mobile device 130, and in communication with the backend server110. The process 400 can be performed during day-to-day activities ofusers of these devices.

At stage 1005, the client application 122 receives an input from a uservia a user interface of a user device. The received input comprisesinformation indicative of a selection of an electronic template. Theelectronic template is one of the electronic templates created using theprocess 400 of FIG. 4.

FIG. 11 shows a screenshot 1100 of an exemplary user interface forallowing a user to input the selection of the electronic template atstage 1005. The screenshot 1100 depicts views if images of respectiveforms of available blank templates. The available templates includetemplates 1105, 1110, 1115, 1120, 1125 and 1130. The user can select oneof the blank templates 1105-1130 by clicking with a mouse or tapping atouch screen, for example.

As an alternative to picking a blank template from the screenshot 1100,the user could select an existing, partially filled-in, template fromthe list of templates 910 shown in the screenshot 900 of FIG. 9. Theuser can select one or more of the templates in the template list 910 bychecking one of the boxes next to the name of the desired templates.

At stage 1010, the client application 122 retrieves an electronictemplate from the memory 125, the template/forms database 135 or fromthe backend server 110 and the template database 160 (or the formsdatabase 170 in the case of a partially filled-in form/template).Alternatively, the client application 122 could receive the electronictemplate from another user device. Receiving a partially completedelectronic form/template from another user device could be done, forexample, when a transfer of responsibility for completing a jobassociated with a form is transferred from one user in an organizationto another user.

At decision block 1012, the client application determines whether torender the electronic template in Form View or Field view. The decisioncould be made without user input be determining a type of user devicethat the selection is coming from and rendering a default view. Adefault view for a smart phone could be the Field View. A default viewfor a tablet could be either the Form View or the Field View, asdetermined by user settings, for example. Alternatively, the clientapplication 122 could request a selection of the type of view from theuser via the user interface of the user device.

If the client application determines that a Form View should berendered, the process 1000 continues at stage 1015, where the clientapplication 122 causes the background image of the selected template tobe displayed on a display of the user device. At stage 1020, theplurality of input fields in the selected template are displayed insuperimposed fashion over corresponding fields on the image of theselected form. FIG. 12 shows a screenshot 1200 of a form selected atstage 1005 and rendered at stages 1015 and 1020. The superimposed inputfields are illustrated in a first Table 1210 and a second Table 1220where cells containing values of “0.00” are input fields that areconfigured to determine values based on values of other cells in theTables 1210 and 1220. Since none of the other cells in the Tables 1210and 1220 have values, the computations default to a value of 0.00.

If, at decision block 1012, the client application determines that aField View is desired, the process 1000 continues at stage 1022 and theclient application 122 renders a Field View list of the input fields ofthe selected template. FIG. 13 shows an example of a Form View 1310 andthe corresponding Field View 1320 of the same template.

At stage 1025, the user interacts with the user interface of the clientapplication 122 to select one of the input fields to receive input fromthe user. The method of input for an individual input field isdetermined by the field type used to create the template. The inputmethods are described above in reference to the field types selected atstage 410 of the process 400 in FIG. 4. At stage 1030, the clientapplication receives the user input for the selected input field(s) viathe user interface specified by the field type of each input field. Theuser can input information to the input fields of the template at stages1025 and 1030 without internet access or other connection to the backendserver 110. When internet access or other type of connection isavailable, the backend server 110 and the user device can synchronizewith the transfer of the information.

If the input field is of the Image field type or the Sketch field type,the input could be an image. In this case, the image can be obtained viaa camera on the user device.

At stage 1030, some field types may trigger screen prompts to facilitatethe data capture process. Captured information can be edited at any timeby re-selecting the field. When saved by the user, all data captured iswritten to the local memory 125 on the device or on the template/formsdatabase 135 of the non-mobile device 130 at stage 1035. The completedform is also communicated to the backend server 110 which stores thecompleted form in the forms database 170. FIG. 14 shows a completed form1400. Once a form is stored at stage 1035, a user may select an actionbutton giving them the option to email the form to one or more users orgenerate a Portable Document Format (PDF) version of the document thatcan then be printed or uploaded to a third-party electronic storagesystem. In addition, other devices in the account can synchronize withthe backend server 110 to retrieve the completed form.

The form may not be fully completed when a user is finished with theform. In this situation, a partially completed form can be transferredin responsibility from user to another user. A first user starts theform, finishes his portion and he can transfer it to a second user. Upontransfer to the second user, the form disappears from the first user'sForms tab (see FIGS. 6 and 7, for the Forms tab) of the user interfaceof the client application 122 and appears on the second user's Formstab. The second user then takes responsibility for filling out the formusing the process 1000 along with doing any tasks that are required. Thesecond user can then transfer the form back to the first user, etc. Thisis a convenient way for communicating that a first task is done and thesecond task can be performed by a different user than the user thatfinished the first task. Such transfer of forms can be done withoutconnection to the backend server 110 via WiFi, for example.

At stage 1040, the client application receives an instruction from theuser device to switch from the current view, either Form View or Fieldview, to the other view. The user may wish to switch from Field View toForm View when he thinks he has completed filling out a form on a smartphone in order to view the electronic form with the background image asa reassurance that all fields are completed. At stage 1045, the clientapplication 122 renders the electronic form in the selected Field Viewor Form View. FIG. 13 shows an example Form View 1310 and thecorresponding Field View 1320 that can both be rendered at stage 1045.

When switching from Form View to Field View at stage 1045, the imagesand sketches can be selectively viewed from the Field View by clickingon them. Likewise, tables can be similarly viewed in this manner.

The process 1000 is exemplary only and modifications to the process 1000can be made without departing from the scope of the methods describedherein. For example, stages may be omitted, added or rearranged.

Referring to FIG. 15, a process 1500 for creating a report usinginformation obtained from forms created by the processes 400 and 1000 ofFIGS. 4 and 10 includes the stages shown. At stage 1505, the clientapplication 122 receives a selection of one or more electronic templatesto include in a report. FIG. 16 shows a screenshot 1600 of a userinterface used to make selections of templates at stage 1505.

The screenshot 1600 is displayed when a user selects a Reports tab 1605in the user interface to create a report. The screenshot 1600 displays asection 1620 of selectable form templates. A pull down menu 1615 iscurrently displaying a Shared Fields selection and a list 1625 of theavailable shared fields is displayed in the section 1620. The sharedfields are those fields that the current user, or other users in thecurrent user's account have made available in other forms. The sharedfields list 1625 appears by default since these fields are availablewithout selecting a template.

The pull down menu 1615 can be used to display a list of any of thetemplates used to create forms on the user device and then select any ofthe templates to be included in the report. By selecting a certaintemplate in the pull down menu list (see list 1710 in FIG. 17) to beinclude in a report at stage 1505, every instance of a form created byany user in the user's account can be utilized to populate the reportwith information. A user can create reports by obtaining informationfrom all the forms listed in a forms tab 1610 or from the forms in thedatabase 170 that are associated with the user's account.

FIG. 17 shows a screenshot 1700 showing a list of available templates1710 in the pull down menu 1615. A user can choose from any templates inthe list 1710 to generate a report. After a user selects one of thetemplates, a list of all the fields in the one selected template aredisplayed in a list 1825, as illustrated in FIG. 18.

After selecting the templates at stage 1505, the process 1500 continuesto stage 1510 where the client application 122 receives a selection ofinput fields that are available in the shared fields and any fieldsincluded in the selected templates. FIG. 18 shows a screenshot 1800where a user has selected one template from the pull down menu 1615, thetemplate entitled “Sample Template—ACME . . . ”. FIG. 18 displays thelist of Shared Fields 1625 and a list of fields 1825 available in theselected template 1820 entitled “Sample Template ACME . . . ” The usercan choose any of the fields in the shared fields list 1625 or any ofthe fields in the list of fields 1825 of the “Sample Template ACME . . .” template to add to the report.

FIG. 19 shows the screenshot 1800 where a user is using a drag-and-dropmethod to select a Customer Contact field 1905 from the ACME list 1820and drag it to a report editor canvas 1920 (as indicated by an arrow1910) to be entered as a report entity 1915. The user can continue todrag-and-drop as many fields as desired from the lists 1625 and 1825. Asone or more fields is added to the report editor canvas 1910, a list offorms (draft forms and completed forms) 1930 appears on the editorcanvas 1910. The list 1930 includes all instances of forms that includethe fields that have been added to the editor canvas 1910.

After a user has selected templates at stage 1505 and fields at stage1510, the process 1500 continues at stage 1515 where the user can reducethe number of form instances listed in the list 1930 of the editorcanvas 1910. A user can activate the filter method by selecting an“Apply Filter” button 1930. FIG. 20 shows a screenshot 2000 that isdisplayed by the client application 122 at stage 1515 in response to auser selecting the Apply Filter button 1930. At stage 1515, the clientapplication 122 receives filter information to enable a directed searchfor fields in completed forms of the types previously selected (SharedFields and Sample Template—ACME in this example). A pull down menu 2005shows a “Completed Date” selection to which the user can selectbeginning and ending dates in a beginning date field 2015 and an endingdate field 2025. The user can further narrow the filter search byspecifying the name of fields in a second pull down menu 2010, andfields 2020 and 2030 that allow the user to search for the selectedfield listed in the pull down menu 2010 that is characterized by certaintext. For example, the screenshot 2000 shows a user searching for anyfields named Customer PO# that start with a number 1. When the user hasnarrowed the search to arrive at only the desired fields, the userreturns to the screenshot 1900 of FIG. 19.

The user can continue to reduce the number of form instances by addingmore filters for different fields in the pull down menu (see pull downmenus 2005 and 2010). A user can remove one of the added filters byselecting a remove button 2035.

After the user has completed the drag-and-drop selections and the filterselections of templates and fields at stages 1510 and 1515, and thefiltering of form instances at stage 1515, the process 1500 continues tostage 1520 where the client application 122 retrieves report informationfrom the shared fields and form instances corresponding to the selectedtemplates, selected fields and selected filter information. At stage1525, the client application 122 stores the information retrieved atstage 1520 to the memory 125, the template/forms database 135 and/orcommunicates the retrieved information to the backend server 110 to bestored in the forms database 170.

At Stage 1530, the client application receives user input to create oneor more charts, tables and/or computations based on the data retrievedat stage 1520. FIG. 21 shows a screenshot 2100 that shows a chart wizardwhere a user can create a chart such as a pie chart, a bar graph, a linegraph, etc. using the user interface shown in the screenshot 2100.

The process 1500 allows a user to create a report without any existingknowledge as to what data is available. Once a user sees what draftforms and completed forms have been retrieved based on the templates andfields selected at stages 1505 and 1510, the user can selectivelyeliminate unwanted forms using the filters at stage 1515 so as to createthe report to show only what they want to show. The user interfacesallow a user to choose one or more templates, create a report to includeany desired fields in the selected templates and any shared fields, andquery across all existing forms, draft forms and/or completed forms, tobring in all data corresponding to the selected fields.

The process 1500 is exemplary only and modifications to the process 900can be made without departing from the scope of the methods describedherein. For example, stages may be omitted, added or rearranged.

As described above, a user can create a template using the process 400and the template can be configured by the user to automatically triggercertain prescribed events when certain trigger events occur. FIGS. 22-24show various screenshots of user interfaces used to create and managethese events and triggers. For example, a template could be configuredto automatically Email a list of users when a form based on one of thetemplates is completed. The client application 122 can create a PDF ofthe completed form and the resulting PDF image can be emailedautomatically to the list of users.

FIG. 22 shows a screenshot 2200 of the template tab used to create atemplate using the process 400 described above. At stage 410, when theuser is specifying the parameters of input fields and the like, the usercan select a Manage Events button 2210. In response, the clientapplication 122 displays screenshots 2300 and 2400 shown in FIGS. 23 and24, respectively. The user interface provided by the screenshots 2300and 2400 allow a user to fully configure what type of trigger eventsoccurring during the filling-out of a form/template will result in anevent such as a generation of an Email, a text message, a generation ofa report, etc.

Specific details are given in the above description to provide athorough understanding of the embodiments. However, it is understoodthat the embodiments may be practiced without these specific details.For example, circuits may be shown in block diagrams in order not toobscure the embodiments in unnecessary detail. In other instances,well-known circuits, processes, algorithms, structures, and techniquesmay be shown without unnecessary detail in order to avoid obscuring theembodiments.

Implementation of the techniques, blocks, steps and means describedabove may be done in various ways. For example, these techniques,blocks, steps and means may be implemented in hardware, software, or acombination thereof. For a hardware implementation, the processing unitsmay be implemented within one or more application specific integratedcircuits (ASICs), digital signal processors (DSPs), digital signalprocessing devices (DSPDs), programmable logic devices (PLDs), fieldprogrammable gate arrays (FPGAs), processors, controllers,micro-controllers, microprocessors, other electronic units designed toperform the functions described above, and/or a combination thereof.

Also, it is noted that the embodiments may be described as a processwhich is depicted as a flowchart, a flow diagram, a data flow diagram, astructure diagram, or a block diagram. Although a flowchart may describethe operations as a sequential process, many of the operations can beperformed in parallel or concurrently. In addition, the order of theoperations may be re-arranged. A process is terminated when itsoperations are completed, but could have additional steps not includedin the figure. A process may correspond to a method, a function, aprocedure, a subroutine, a subprogram, etc. When a process correspondsto a function, its termination corresponds to a return of the functionto the calling function or the main function.

Furthermore, embodiments may be implemented by hardware, software,scripting languages, firmware, middleware, microcode, hardwaredescription languages, and/or any combination thereof. When implementedin software, firmware, middleware, scripting language, and/or microcode,the program code or code segments to perform the necessary tasks may bestored in a machine readable medium such as a storage medium. A codesegment or machine-executable instruction may represent a procedure, afunction, a subprogram, a program, a routine, a subroutine, a module, asoftware package, a script, a class, or any combination of instructions,data structures, and/or program statements. A code segment may becoupled to another code segment or a hardware circuit by passing and/orreceiving information, data, arguments, parameters, and/or memorycontents. Information, arguments, parameters, data, etc. may be passed,forwarded, or transmitted via any suitable means including memorysharing, message passing, token passing, network transmission, etc.

For a firmware and/or software implementation, the methodologies may beimplemented with modules (e.g., procedures, functions, and so on) thatperform the functions described herein. Any machine-readable mediumtangibly embodying instructions may be used in implementing themethodologies described herein. For example, software codes may bestored in a memory. Memory may be implemented within the processor orexternal to the processor. As used herein the term “memory” refers toany type of long term, short term, volatile, nonvolatile, or otherstorage medium and is not to be limited to any particular type of memoryor number of memories, or type of media upon which memory is stored.

Moreover, as disclosed herein, the term “storage medium” may representone or more memories for storing data, including read only memory (ROM),random access memory (RAM), magnetic RAM, core memory, magnetic diskstorage mediums, optical storage mediums, flash memory devices and/orother machine readable mediums for storing information. The term“machine-readable medium” includes, but is not limited to portable orfixed storage devices, optical storage devices, wireless channels,and/or various other storage mediums capable of storing that contain orcarry instruction(s) and/or data.

In conclusion, the teachings disclosed herein provide, among otherthings, a system and method for providing for conversion of paper formsto electronic forms, providing for capturing information in theelectronic forms and managing the electronic forms among a group ofusers. Those skilled in the art can readily recognize that numerousvariations and substitutions may be made in the invention, its use andits configuration to achieve substantially the same results as achievedby the embodiments described herein. Accordingly, there is no intentionto limit the invention to the disclosed exemplary forms. Manyvariations, modifications and alternative constructions fall within thescope and spirit of the disclosed invention as expressed in the claims.

1. A method of interacting with an electronic form, the methodcomprising: receiving, by a processor, an image of a form; receiving, bythe processor, form template information specifying a plurality of inputfields; receiving, by the processor, field view template informationspecifying a plurality of field view input fields; and storing, within amemory, template configuration information including the form templateinformation and the field view template information wherein theelectronic form is configured to be rendered by superimposing arepresentation of ones of the plurality of input fields over the imageof the form; receiving, from among a plurality of electronic formtemplates, a selection of one or more of the plurality of electronicform templates for creating a report wherein at least one of theplurality of electronic form templates includes the form templateinformation; retrieving, by the processor, report information based uponthe form template information; and rendering, by a display device, areport based upon the report information; wherein in response to adetermination to render the electronic form in a field view theplurality of field view input fields are displayed in accordance withthe field view template information and without displaying the image ofthe form;
 2. The method of claim 1 further including: receiving aselection of input fields in the one or more of the plurality ofelectronic form templates for inclusion in the report; wherein theretrieving includes retrieving the report information based also uponthe selection of the input fields.
 3. The method of claim 1 wherein theform template information includes a first input field type selectionand first field location information for a first input field of theplurality of input fields wherein the first input field type selectionis selected from a plurality of input field types and the first fieldlocation information is defined relative to the image.
 4. The method ofclaim 1 wherein the plurality of field view input fields are displayedin response to an order of appearance specified by the field viewtemplate information wherein the order of appearance is different froman order in which the plurality of input fields are rendered relative tothe image of the form.
 5. The method of claim 1 wherein, as between thefield view and a form view in which the plurality of input fields arerendered relative to the image of the form, the field view is a defaultview in which the electronic form is configured to be rendered.
 6. Themethod of claim 3 wherein the image of the form includes a plurality offields, the first field location information corresponding to a positionof a first of the plurality of fields.
 7. A method, comprising:receiving a selection of an electronic form; rendering, by a display ofa device, an image of an original form upon which the electronic form isbased; superimposing a plurality of input fields over a correspondingplurality of fields of the original form; receiving field view templateinformation; storing, within a memory, template configurationinformation including the field view template information and form viewtemplate information specifying the plurality of input fields; selectingone of the input fields to receive user input; receiving, from among aplurality of electronic form templates, a selection of one or more ofthe plurality of electronic form templates for creating a report whereinat least one of the plurality of electronic form templates includes theform template information; and retrieving, by the processor, reportinformation based upon the template configuration information; andrendering, by a display device, a report based upon the reportinformation; wherein in response to a determination to render theelectronic form in a field view the plurality of input fields aredisplayed in accordance with the field view template information andwithout displaying the image of the form;
 8. The method of claim 7wherein the field view template information specifies an order ofappearance of the plurality of input fields in the field view andwherein the order of appearance is different from an order in which theplurality of input fields are rendered relative to the image of theform.
 9. A system for interacting with an electronic form, the systemcomprising: memory; a network interface; and a processor coupled to thememory, the processor being configured to: receive an image of a form;receive form template information specifying a plurality of inputfields; receive field view template information specifying a pluralityof field view input fields; and store, within the memory, templateconfiguration information including the form template information andthe field view template information wherein the electronic form isconfigured to be rendered by superimposing a representation of ones ofthe plurality of input fields over the image of the form; receive, fromamong a plurality of electronic form templates, a selection of one ormore of the plurality of electronic form templates for creating a reportwherein at least one of the plurality of electronic form templatesincludes the form template information; retrieve report informationbased upon the form template information; and render a report based uponthe report information; wherein in response to a determination to renderthe electronic form in a field view the plurality of field view inputfields are displayed in accordance with the field view templateinformation and without displaying the image of the form;
 10. The systemof claim 9 wherein the processor is further configured to: receive aselection of input fields in the one or more of the plurality ofelectronic form templates for inclusion in the report; wherein theretrieving includes retrieving the report information based also uponthe selection of the input fields.
 11. The system of claim 9 wherein theform template information includes a first input field type selectionand first field location information for a first input field of theplurality of input fields wherein the first input field type selectionis selected from a plurality of input field types and the first fieldlocation information is defined relative to the image.
 12. The system ofclaim 9 wherein the plurality of field view input fields are displayedin response to an order of appearance specified by the field viewtemplate information wherein the order of appearance is different froman order in which the plurality of input fields are rendered relative tothe image of the form.
 13. The system of claim 11 wherein the pluralityof input field types includes a database field type related to a storedgroup of entities wherein one or more of the stored group of entitiesare displayed in response to user entry of information into the firstinput field and wherein the processor is further configured to receive,via the network interface, a database file containing the stored groupof entities.
 14. The method of claim 1 wherein the determination torender the electronic form in a field view is made based uponcharacteristics of a device rendering the electronic form.
 15. Themethod of claim 1 wherein the determination to render the electronicform in a field view is made based upon user input selecting the fieldview.
 16. The method of claim 1 wherein the form template informationfurther specifies a trigger event, the method further includingperforming a prescribed event upon occurrence of the trigger event. 17.The method of claim 16 wherein the trigger event comprises receivinguser input for at least one of the plurality of input fields.
 18. Themethod of claim 17 wherein the prescribed event comprises sending aversion of the electronic form including at least the user input. 19.The method of claim wherein the trigger event comprises receiving userinput for each of the plurality of input fields and wherein theprescribed event comprises sending a completed version of the electronicform.